
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% This is a template for constructing your project plan document, but
% also to show the use of the l3deliverable class. Use pdflatex and
% bibtex to process the file, creating a PDF file as output (there is
% no need to use dvips when using pdflatex).
%
% Several meta data commands have been implemented to collect
% information such as deliverable identifier, project name etc (see
% below the \date command.

\documentclass{l3deliverable}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% You can use the svn-multi package to automatically insert version
% control information into your document (an example of how to do this
% is shown below).  Make sure to set the 'svn:keywords' subversion
% property to 'Id' for the source file, for example, type:
%
% svn propset svn:keywords 'Id' d1.tex
%
% in the same directory as your 'd2.tex' file. 
%
% The information between the two $$ will now be updated when you next
% commit the file to your SVN repository.
%
% You can of course, just use this field to insert manual version
% information, e.g. 1.2, 1.2.1 ... instead.

\usepackage{svn-multi}
\svnid{$Id: d1.tex 44 2011-11-17 01:07:28Z 0906578c $}
\version{SVN Revision \svnrev~ \

Made \svnday/\svnmonth/\svnyear~ by \svnauthor}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\usepackage{url}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%% Check these macro values for appropriateness for your own document.

\title{Team Organisation}

%%authors
\author{
  Daniel Callander \\
  Stephen McQuistin \\
  Ian Scott \\
  Agnieszka Kielbinska \\
  David Newall}

%%release date 
\date{29 September 2011}

\deliverableID{D1}
\project{PSD3 Group Exercise 1}
\team{K}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\begin{document}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\maketitle

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%% Standard section for all documents

\section{Introduction}

\subsection{Identification}

This is the management plan for Team \emph{Special} K.

\subsection{Related Documentation}

\begin{list}{}{}
\item PSD3 Group Exercise Description \  
  \url{http://fims.moodle.gla.ac.uk/file.php/128/assessment/ge-1.pdf}
\end{list}
 
\subsection{Purpose and Description of Document}
This document is to explain how we will organize our team, defining roles,
authority and ways of communcation, as well as their associated risks.

\subsection{Document Status and Schedule}

This document is a draft and will be revised as neccessary. Last updated 2011/10/11.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\section{Roles}

We decided to use the laissez-faire model as we all have a similar skillset. 
This means we will share the different roles between us and assign them as required depending on the task at hand and other factors such as previous experience at that particular task. 
Even though we have chosen this particular model, we do need to assign some administrative roles, which are as follows:
\begin{description}
    \item[Secretary] This role has been assigned to Daniel. He will take notes in situations where it is required, as well as taking minutes for meetings. 
    \item[Editor] This role has been assigned to Stephen. He will take our split LaTeX documents for our deliverables and combine them to produce one single document.
\end{description}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\section{Authority}

There will be no single leader in our team, as the laissez-faire model implies. 
All decisions must be made through groupdiscussion and if need be, a vote will be 
held to settle any argument, and as there are five of us, there will always be a majority. 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\section{Communication}

We have set up a regular weekly meeting time of \emph{Monday 4pm} and \emph{Tuesday 11am}. Notes will be taken at this meeting so we have a record of what was said. We have each other's email address and phone numbers for communication outside of the meeting. An IRC channel has also been set up on \emph{irc.freenode.org \#teamk} so we can communicate online easily. Chat logs from IRC are saved per client, so each of us has our own archive of what was said.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\section{Information Management}

A Google Docs collection has been set up and shared amongst the team. 
This will let us share documents and files between us easily.
We also have the shared lab filespace which will have an SVN repository on it to keep track of our files.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\section{Organisational Risks}

Since there is no rigid structure or specific leader, there is a danger that there might not be a clear coordination between group members. 
There may also be an issue if every member has a different idea and we are unable to come to a consensus. 
One possible risk is that there could be a disagreement within the team, making it difficult to make decisions.
A solution for this would be to have a 'cool down' period where we step back from the project for a short while to think things through clearly (\emph{i.e: go to the pub}).
Another risk would be one of the team members falling ill.
The solution for this would be to keep a bit of slack time free incase this happens, and also keep that member up to date what is going on within the team.
As most of the documents are available online, this should be no problem.
A third risk would be if a team member does not put in the required work.
To solve this we will have a discussion with that team member and let them know of the problem.
Beyond this, not much can be done and we will simply need to work harder. 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\appendix

\section{Glossary}

\begin{description}
    \item[IRC] Internet relay chat. A protocol used for internet chat rooms.
\end{description}

\end{document}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
